Automated module cleanup walked the following modules in order
and stopped after accumulating at least 10 modified files:

• executors:testing
• external-annotations:javaagent
• external-annotations:javaagent-unit-tests
• failsafe-3.0:library
• finagle-http-23.11:javaagent
• finatra-2.9:javaagent
• geode-1.4:javaagent
• google-http-client-1.19:javaagent
• grails-3.0:javaagent
• graphql-java-12.0:javaagent
• graphql-java-12.0:library
• graphql-java-20.0:javaagent
• graphql-java-20.0:library
• graphql-java-common-12.0:library
• graphql-java-common-12.0:testing
• grizzly-2.3:javaagent

---

Module: executors:testing

Module path: instrumentation/executors/testing

Summary

No safe repository-guideline fixes were needed for instrumentation/executors/testing; all scoped reviewable files already conformed to the loaded cleanup rules.

Applied Changes

No safe automated changes were applied.

Module: external-annotations:javaagent

Module path: instrumentation/external-annotations/javaagent

Summary

No safe repository-guideline fixes were needed under instrumentation/external-annotations/javaagent; no files were changed.

Applied Changes

No safe automated changes were applied.

Module: external-annotations:javaagent-unit-tests

Module path: instrumentation/external-annotations/javaagent-unit-tests

Summary

No safe repository-guideline fixes were found under instrumentation/external-annotations/javaagent-unit-tests; no files were changed.

Applied Changes

No safe automated changes were applied.

Module: failsafe-3.0:library

Module path: instrumentation/failsafe-3.0/library

Summary

No safe repository-guideline fixes were applied under instrumentation/failsafe-3.0/library; the in-scope files already match the loaded style, library, testing, Gradle, and metadata.yaml review guidance.

Applied Changes

No safe automated changes were applied.

Module: finagle-http-23.11:javaagent

Module path: instrumentation/finagle-http-23.11/javaagent

Summary

No safe fixes were applied. The only deterministic cleanup candidate was reverted because validation showed it needs a manual muzzle/version-boundary decision.

Applied Changes

No safe automated changes were applied.

Unresolved Items

File: build.gradle.kts
Reason: `gradle-conventions.md` requires `assertInverse.set(true)` for bounded muzzle ranges like `[23.11.0,)`, but adding it caused `./gradlew :instrumentation:finagle-http-23.11:javaagent:muzzle` to fail because older `finagle-http` versions unexpectedly passed inverse validation; determine the correct muzzle/version boundary before adding `assertInverse.set(true)`.

Module: finatra-2.9:javaagent

Module path: instrumentation/finatra-2.9/javaagent

Summary

Applied safe cleanup in FinatraSingletons.java and committed it as 92dbf8df (Cleanup for finatra-2.9 javaagent).

Applied Changes

Style

File: FinatraSingletons.java:27
Change: Renamed the private static final `VirtualField` handle from `callbackClassField` to `CALLBACK_CLASS` and removed the redundant `request.controllerClass() != null` fallback in the span-name extractor.
Reason: The style guide treats `VirtualField` handles as constant-like semantic handles that should use `SCREAMING_SNAKE_CASE`, and nullability guidance discourages defensive null checks for values exposed by non-`@Nullable` APIs such as `FinatraRequest.controllerClass()`.

Module: geode-1.4:javaagent

Module path: instrumentation/geode-1.4/javaagent

Summary

No safe fixes were applied. The only deterministic candidate, adding assertInverse.set(true) to the bounded muzzle pass, was reverted because :instrumentation:geode-1.4:javaagent:muzzle showed the instrumentation passes pre-1.4.0 Geode versions where failure was expected.

Applied Changes

No safe automated changes were applied.

Unresolved Items

File: build.gradle.kts
Reason: `muzzle` uses `versions.set("[1.4.0,)")` without `assertInverse.set(true)`, which normally violates the Gradle convention for bounded `pass` ranges; adding it caused inverse muzzle failures because `GeodeInstrumentationModule` still passes `geode-core` `1.0.0-incubating` through `1.3.0`. Manual version-boundary work is needed before `assertInverse.set(true)` can be enabled.

Module: google-http-client-1.19:javaagent

Module path: instrumentation/google-http-client-1.19/javaagent

Summary

Applied one safe cleanup fix and committed it in c77015df (Cleanup for google-http-client-1.19 javaagent).

Applied Changes

Config

File: metadata.yaml:26
Change: Added `declarative_name: java.common.peer_service_mapping` for `otel.instrumentation.common.peer-service-mapping`.
Reason: `metadata-yaml-format.md` requires each `metadata.yaml` config entry to include the correct declarative config path; sibling HTTP client metadata uses `java.common.peer_service_mapping` for this shared property.

Module: grails-3.0:javaagent

Module path: instrumentation/grails-3.0/javaagent

Summary

Applied one safe cleanup in instrumentation/grails-3.0/javaagent and committed it as 68bbcf3c (Cleanup for grails-3.0 javaagent).

Applied Changes

Javaagent

File: UrlMappingsInfoHandlerAdapterInstrumentation.java:8
Change: Static-imported `GrailsServerSpanNaming.serverSpanName()` and used the accessor unqualified at the `HttpServerRoute.update(...)` call site.
Reason: The javaagent singleton holder guideline says exported singleton accessors should be static-imported and called unqualified from callers.

Module: graphql-java-12.0:javaagent

Module path: instrumentation/graphql-java/graphql-java-12.0/javaagent

Summary

Applied and committed one safe cleanup for graphql-java-12.0 javaagent.

Applied Changes

Javaagent

File: GraphqlInstrumentation.java:40
Change: Qualified the `GraphqlSingletons.addInstrumentation(...)` helper call and removed the static import of `addInstrumentation`.
Reason: `javaagent-singletons-patterns.md` says callers should static-import only stored singleton accessors or uppercase constant-like fields, not non-accessor helper methods that perform work.

Module: graphql-java-12.0:library

Module path: instrumentation/graphql-java/graphql-java-12.0/library

Summary

No safe repository-guideline fixes were found under instrumentation/graphql-java/graphql-java-12.0/library; no source changes were applied.

Applied Changes

No safe automated changes were applied.

Module: graphql-java-20.0:javaagent

Module path: instrumentation/graphql-java/graphql-java-20.0/javaagent

Summary

Applied one safe cleanup fix and committed it as Cleanup for graphql-java-20.0 javaagent.

Applied Changes

Build

File: build.gradle.kts:32
Change: Added `metadataConfig` for the default `test` task and updated `testDataFetcher` so collected telemetry is labeled with both active GraphQL config flags.
Reason: Gradle metadata collection guidance requires `metadataConfig` to describe non-default `jvmArgs`; this module enables `otel.instrumentation.graphql.operation-name-in-span-name.enabled=true` for all test tasks and `otel.instrumentation.graphql.data-fetcher.enabled=true` for `testDataFetcher`.

Module: graphql-java-20.0:library

Module path: instrumentation/graphql-java/graphql-java-20.0/library

Summary

Applied and committed one safe cleanup in graphql-java-20.0 library: normalized single-test-task Gradle configuration from tasks.withType<Test>().configureEach to tasks.test.

Applied Changes

Build

File: build.gradle.kts:18
Change: Changed the JVM argument configuration block from `tasks.withType<Test>().configureEach` to `tasks.test`.
Reason: `gradle-conventions.md` says single-test-task modules should use `tasks.test`; `withType<Test>().configureEach` is reserved for modules with explicit additional `Test` tasks.

Module: graphql-java-common-12.0:library

Module path: instrumentation/graphql-java/graphql-java-common-12.0/library

Summary

Applied one safe cleanup in graphql-java-common-12.0 library and committed it.

Applied Changes

Semconv

File: OpenTelemetryInstrumentationHelper.java:44
Change: Replaced direct imports of `ExceptionAttributes.EXCEPTION_MESSAGE` and `ExceptionAttributes.EXCEPTION_TYPE` with copied local `AttributeKey` constants.
Reason: Repository semconv rule requires library instrumentation to copy semantic convention constants directly instead of depending on the semconv artifact.

Module: graphql-java-common-12.0:testing

Module path: instrumentation/graphql-java/graphql-java-common-12.0/testing

Summary

Applied one safe cleanup in AbstractGraphqlTest.java to use more idiomatic AssertJ assertions for single GraphQL error checks.

Applied Changes

Testing

File: AbstractGraphqlTest.java:255
Change: Replaced `hasSize(1)` plus `get(0)` assertions with AssertJ `singleElement().satisfies(...)` for parse and validation error checks.
Reason: `testing-general-patterns.md` prefers idiomatic AssertJ collection assertions over manual size checks and indexed element extraction.

Module: grizzly-2.3:javaagent

Module path: instrumentation/grizzly-2.3/javaagent

Summary

Applied and committed two safe cleanup fixes for instrumentation/grizzly-2.3/javaagent.

Applied Changes

Build

File: build.gradle.kts:31
Change: Changed the single test task configuration from `withType<Test>().configureEach` to `test`.
Reason: `gradle-conventions.md` says single-test-task modules should use `tasks.test`; `withType<Test>().configureEach` is reserved for modules with explicit custom `Test` tasks.

Javaagent

File: FilterInstrumentation.java:54
Change: Removed unused `@Advice.This BaseFilter it` parameters and the now-unused `BaseFilter` import.
Reason: Repository general/style guidance favors removing unused code and keeping advice method signatures to only the parameters needed by the advice body.

---

Download module cleanup diagnostics